If im correct in thinking you mean trap every error possible in code eg:
int*p=getstuff();
if(p) use(p); else MessageBox(0,"eeee","aaaaagh!",MB_ICONERROR|MB_OK);
Well, depends on the language, the critical nature of the tasks, the speed and size requirements scale of the program..and quality of your debugging tools.
Really its about time: A company would want to minimise risks of having an error in the first place, and in the event of having one, be able to find it easily (of course). The larger something is, the more blablabla <i knwo...its all obvious ..>. Basically, after years of experience in a particular fashion, a fusion between the directing programmer and physical coders can judge whats best.
And if your going to if for an exception...why not else. May as well just not do the if in the first place: at least that way it would crash and you would know theres a problem. Ifing and nothing happening gives no no idication of an exception, more something logically incorrect which could lead someone seeking through all their code.