The funny part is, if you divided by zero, usually the problem was getting a zero to divide with, not the fact that you want to use it in the division.
So allowing the calculation to proceed isn't helpful, what you might want to do is go back and figure out why you got a zero to begin with.
In signal processing code, they often use the NaN for this and keep going if that's what is necessary. This isn't a new concept.
LONG RESPONSE: That is exactly what I did when I encountered a Divide-by-zero error in some GPS code. The fix was to assume GPS was unavailable at that particular space-time instant, since the satellite positions resulted in a near-singular navigation matrix.
SHORT RESPONSE: If you're dividing by zero, the problem's probably buggered anyway.
Shouldn't that be NaNO2, decomposing to NaNO3? :-P
Shouldn't that be NaNO2, oxidizing to NaNO3? :-P