another option i would like to see is in the "Debugging Settings" a way to disble the error handling, thus when it breaks you can track exactly what sequence of events led to it happening during the testing phase.

not just "oh look, there's anerror in the log..." but "hey, when i click here something go's wrong".

the slowdown that occurs with the exception is pretty generic and could be due to a variety of reasons, not necessarily an error.

not to mention throwing an exception would allow it to be caught in visual studio and debugged.