Build failure from Microsoft.AspNetCore.Routing.Microbenchmarks (reason: 'AllMeasurements')

Filing as part of buildops.

Build failure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=924728 (see the `Windows x64` job)

Error: `Microsoft.AspNetCore.Routing.Microbenchmarks.dll -f * --validate-fast" exited with code 1`

Possibly due to this preceding issue: `'JumpTableMultipleEntryBenchmark.Dictionary: Dry(Toolchain=InProcessNoEmitToolchain, IterationCount=1, LaunchCount=1, RunStrategy=ColdStart, UnrollFactor=1, WarmupCount=1) [Count=100], 0 runs' failed, reason: 'AllMeasurements'`

This clearly appears to be an intermittent failure (it didn't also happen on the previous or next build). However our "intermittent failures" across the whole stack are reaching a critical mass where a large fraction of builds are failing, so I think we'll have no choice but to investigate them or disable problematic components.

@joperezr Does your team own ASP.NET Core routing these days? Or is it still @mkArtak as listed in [area owners](https://github.com/dotnet/aspnetcore/blob/4adfd0e05efdec201e417ec4800cfd6f67c61e78/docs/area-owners.md)?

Start with the linked Azure DevOps build's Windows x64 job and the Microsoft.AspNetCore.Routing.Microbenchmarks.dll invocation using --validate-fast. Inspect the JumpTableMultipleEntryBenchmark.Dictionary case and its AllMeasurements result; done means the benchmark failure is resolved or the problematic component is explicitly disabled.

Written by the indexing model from the issue text.