EvalException is enabled and RegistryManager and or EvalException detect an
unexpected exception, they'll call StackedObjectRestorer to:
o save the Registry state
o change currently registered StackedObjectProxies to detect when they're being
used within the interactive debugger via a threadlocal (resulting in a small
performance hit). They'll get their proxied object from the restorer when they
detect the presence of the debugger, otherwise they'll continue to work as
normal