This is totally a case of "broken when you found it", but do we really want to silently ignore super-class statements whose names are lexically hidden by derived class statements. These base class statics are still easily accessible from base class methods that could be called by (or even could BE) the "run" method. Do we have a negative test that demonstrates a safe landing when you try to queue and execute this kind of hidden and passed-over statement?