Good point. It did start as something akin to that and I forgot that over time I've adapted the approach to catch things left in by other developers (and already committed to the codebase).
Given the catching the debug statement is limited to my very specific usage, your suggestion would be more suitable.
Given the catching the debug statement is limited to my very specific usage, your suggestion would be more suitable.