I have to say it - developer error :)

as of now its a dead link - might want to fix it

Comparing apples to pine cones.

The original article stated that the try catch construct didn't add significant overhead which it DOES NOT. In your code example it is the error being thrown and handled that causes the delay not the try catch itself, if you did not cause the error to be thrown the performance would be close to the performance without the try catch (In my code, I have been unable to measure the difference in milliseconds).

misleading and incorrect article.

Well Done