The code was previously using the real SymbolTableImpl's representation to analyze a StatName and determine which segments were dynamic and which were symbolic. Due to the details of the symbol-table's byte representation, this was working for all known cases,

However, fuzzing found some corner-cases where this wound up being misinterpreted. I don't think these currently can occur, but using the class-hierarchy correctly avoids this problem.