Split build stage into loading SymbolSlab from file and actual index building stage to simplify benchmarking distinct parts of index builds.
As for the memory consumption "benchmark", while this looks like misuse of benchmark library, this can be still when experimenting with index compression techniques as discussed offline.
Also, switch to ms for benchmark measurements time units and fix incorrect logger message ( BackingMemorySize is not initialized to correct value when the logger is called, callers should be responsible for memory usage logging).
The hack might not be obvious for other people who run these benchmarks. Is it possible to print some extra message along with the result to explain the hack?