BTW,

I found this related submission on MS Connect: Incorrect error number passed to catch block

Please go there and vote for it as an important issue. (You'll have to login with an MS Live account.)

Maybe MS will address it in an upcoming release or service pack...