A report can return the right numbers and still do unnecessary work. Repeated text += next copies a growing immutable string. Repeated enumeration can rerun a query, reopen a feed, or fail when the source can only be consumed once.
Start with those observable costs before changing syntax.
Use StringBuilder when you append pieces incrementally, a dictionary when you need repeated lookups, and a set when you need membership. These choices have costs of their own, so keep the output and ownership rules visible. A dictionary doesn't automatically decide whether the first or last duplicate wins.
The checks count source reads, comparer calls, and managed bytes allocated after warmup. They don't claim a production speedup from browser timings. Measure a representative workload in its deployment environment before making that claim.
A builder accumulates text; an index retains the last value for each key. The exercises also check exact output formatting.