reverses the introduction of catchAndReportExceptions

Back then having a bunch of try/catch blocks in different functions
significantly slowed down the compilation, but:
1) That's only relevant to -optimize
2) Having catchAndReportExceptions + a closure for every convertion
stack frame very much pollutes the stack trace