disallow Session /state alteration when flush context actually executing ?

this might be tricky. Basically intercept add(), delete(), _attach() and cascading events, maybe "dirty" events for objects already flushed too (tricky!). this would be based on being inside of flush_context.execute().

But it would be awesome, all those docs everyone doesn't read about mapper events wouldn't be so critical anymore.