Well, that does not help if the line in question is what you want to examine.The usual workaround, which Craig used, is to place the breakpoint after the offending line which gives the library a chance to reset the context.
I think we must make "usual" the inclusion of explicit card and stack references where none should be needed, but where they now and then seem to be required. If "now and then" seems harmless and innocuous, I am little comforted by the fact that I have an awful lot of code that does not have this sort of treatment, never did nor needed to, and I fear that a standalone might fail.