We are currently always wrapping ContainerModificationStrategy with an enforcer, even when that enforcer does nothing. The same applies to ListEntryModificationStrategy.

Improve the situation by only wrapping when an enforcer is actually needed – hence we either use stock methods, or run an enforcer inbetween. This has the benefit of making MandatoryLeafEnforcer a singleton implementation, allowing it to be perfectly inlined.

It also means that most of the time we will not encounter an overridden SchemaAwareApplyOperation method, simply because mandatory leaves are not that prevalent.