anchor.diff:  
   === The ConfigUsageStatsSpi
   
  -The methods for managing and tracking of configuration changes are delegated to the current
  -most sinificant implementation of the +org.apache.tamaya.model.spi.ConfigUsageStatsSpi+ SPI.
  +The methods for managing and tracking of configuration changes are similarly delegated to an
  +implementation of the +org.apache.tamaya.model.spi.ConfigUsageStatsSpi+ SPI.
   By implementing this SPI and registerting it with the +ServiceContext+ the usage tracking
   logic can be adapted or replaced.
   
  
positive.code: [source,listing]
  -------------------------------------------------------------------------------
  # Metamodel information
  _config-model.provider=ConfigModel Extension
  
  # org.mycompany.root (optional section)
  _org.mycompany.root.model-type=Section
  _org.mycompany.root.model-description=Root section defining my company configuration.
  
  # org.mycompany.security (required section)
  _org.mycompany.security.model-type=Section
  _org.mycompany.security.model-required=true
  _org.mycompany.security.model-description=Security related settings.\
           refer for further details to XXX.
  
  # minmal section
  _minimal.model-class=Section
  
  # custom validated section
  _validated.model-type=Section
  _validated.model-validator=org.apache.tamaya.model.TestValidator
  -------------------------------------------------------------------------------
  
  Above +org.mycompany.root+ transitively defines 3 sections:
  
negative.code: Usage tracking is disabled by default. It can be enabled by calling +ConfigUsageStats.enableUsageTracking(true);+.
  +ConfigUsageStats.isUsageTrackingEnabled()+ returns the current tracking status.
  
  The +Usage+ class itself provides access to further fainer grained usage data (+AccessDetail+) containing:
  
  * the access point (+fqn.ClassName#method(line: xxx)+).
  * the number of accesses
  