Session.WaitOnHandle loosing call stack

I have seen a number of issues where the call stack provided does not reflect the real location of the exception, making diagnosis nearly impossible.
This is caused by ```Session.WaitOnHandle``` using ```throw _exception;```.