verbose terminate handler

[Benjamin Kosnik]

> A little bit confusing if you don't know that this 'terminate called ...'-thing doesn't alway
> indicate an uncaught exception.

As Jason indicated for your original example, verbose terminate is
behaving as expected: it prints active exception information. 

Since you'd thrown an exception, but then caught it in the catch block,
and called terminate in that same block, the exception is still
considered active. Thus, the message.

Perhaps we should tweak the docs to clarify this situation. What do you think?

-benjamin