So perhaps the eval will do the trick, esp. since one is generally generating a stack trace just before die'ing, so the run-time use of these constructs is not so questionable.
I tried it both ways with no effect, in various scopes. I came to the conclusion, without delving into the innards, that the pragma is not universal, but specific to each scope in which it's used (which makes sense when you think about scope in perl ... e.g. 'use bytes' does not extend to packages you use). So in this case the "no overload" would only be of use in your particular package or class that uses it initially -- dipping into that sans permission, outside of subclassing, would be yet another ugly kludge.
I could of course be missing much here -- it was only a cursory investigation where I twiddled some knobs in a test script/package.
Matt
