[8.5.2] Far too many explicit references to EsCompiler and EsParser

This complaint almost certainly applies to all versions of VA. Almost every reference to EsCompiler is incorrect. There should only be one or two such references.

While some of them are harmless, they represent a misuse of the intended Smalltalk compiler model, namely the global Compiler and the expression Compiler parserClass.

StsPowerTools class>>#parseTreeFor:forCompiledMethod:

StsPowerTools class>>#parseTreeNoCommentsFor:class:
EpPackager>>#isCompilerIncluded
EmMethodEdition>>#compile:in:
EpBaseImageComponentPackagingInstructions class>>#packagingRulesFor:
ClassDescription>>#copy:from:ifNewAddTo:
ClassDescription>>#regenerate:
EsCompiler class>>#initializeAfterLoad (one of the few valid references)
AbtFeatureCtl>>#analyzeFeatureExpression:
Behavior>>#compiler
EmFileOutInterface class>>#fileInSourceFrom:
AbtFeatureLoader class>>#checkIfValidFeature:
EtClassBrowser>>#bytecodesStringFor:
EsParser class>>#parse:class:scanComments:errorHandler:ifFail:

and

StsPowerTools class>>#parseTreeFor:
StsPowerTools class>>#parseTreeFor:forCompiledMethod:
StsPowerTools class>>#parseTreeNoCommentsFor:class:
EtWindow>>#stsInspectParseTree
EsParsing class>>#removing (one of the few valid references)
EsCompiler class>>#initializeAfterLoad (one of the few valid references)
EtAbstractMethodsBrowser>>#stsCopyMessagePattern
CompiledMethod>>#stsParseTree

Any chance of this being corrected for the 8.6.1 release?