Maybe we could also hold the operation queue in `OgmSession` and pass it into the different dialect methods via `TupleContext` and `AssociationContext`? That way the queue reference would always be passed along the stack, not requiring a `ThreadLocal` or similar things.

That would require to pass the actual `OgmSession` into `OgmEventListener` via the flush event (currently one gets the delegate `SessionImpl` there) which I think may be done by overriding `Session#flush()` and `SessionImpl#autoFlushIfRequired()`. I'm just thinking out loud here, not sure whether that'd be really better or even possible at all.