...having typed that out though, I think I know why. Because

record_directory_expansion

implements a cache, only the first iteration of the benchmark is actually having to perform the expansion, and the rest of the runs of the benchmark are using the cached expansion. In practice, I’m not sure how frequently we will hit that cache.