private void initHighlighters() {
		// ability to highlight (with many different colors) the source in the decompiler.
		highlightService = tool.getService(DecompilerHighlightService.class);

		// Start with the ALL highlighter
		CTokenHighlightMatcher matcher = new VertexHighlighter();
		taintProvider.setHighlighter(highlightService, matcher);
	}
The concrete highlighter instances created by Ghidra are ClangDecompilerHighlighters. This class applyHighlights and clearHighlights
using our installed matcher. We are currently caching the query items and the colors that are being applied to maintain consistency in the matcher. There
is no way to reach in to the matcher to clear that cache; this may be useful.  This needs some thought.  One may to do this is to create a completely new highlighter
with a new matcher.  This seems like a bad solution.  The matching itself is done in the TaintProvider which uses TaintState to maintain the current
list of ClangTokens we want to match on based on the query results and filter.

<p>
We create a map of highlighters that can be changed via the gui.  This provides different strategies for a user to highlight the taint results.
Ghidra/Features/DecompilerDependent/src/main/java/ghidra/app/plugin/core/decompiler/taint/TaintPlugin.java