Hey John,
In all our code we optimize for the "valid user doing sane things". That means the fastest code path will always be an activated instance of your app and the user not doing anything stupid on their system.
We don't intend to change the code-flow internally. As-is it throws no exceptions internally for activated and genuine customers with a correctly configured machine. And no exceptions are thrown from a TurboActivate function call (meaning no exceptions will ever bubble up from our API to your app).
Just configure your tools to white-list any exceptions that are caught and handled by TurboActivate.