Actually this is a really good example of where .Net can let you down by making it easy to write a less than optimal solution. Makes me wonder how well LINQ to Object queries really perform.

The article does make the point that using try/catch blocks as program flow is bad design.
I think we can all agree that checking for an exception case and handling it is the best way to write code.

public void doSomething(object something) {
if (something == null)
return;
}

is ALWAYS more efficient than:

try {
doSomething(something1);
} catch (Exception e)
{
wtf(e);
}

Needless to say I think this subject has already been well covered now.