I can't share the entire codebase to reproduce the issue, but I'm using [Visual Studio Diagnostic Tools][0] to inspect performance and operations are taking many times longer to execute that what's getting reported in CPU usage.

### Example Code

Here's an example of the offending block of code between two breakpoints:

[![Diagnostic Entry Point][1]][1]

### Profiling Time

The CPU samples inside this method only suggest it's spending about **1000 ms** to execute:

[![CPU Usage][2]][2]

[![Caller Callee][3]][3]

[![Profile][4l]][4f]

### Execution Time

However, it takes nearly **50 seconds** between breakpoints

[![Diagnostic Timeline][5]][5]

### Question

* What could cause such a long execution timeline that doesn't show up when profiling?

### Things I've Tried:

* Restarting VS
* Restarting Machine
* Reloading Symbols
* Caching Symbols

  [0]: https://learn.microsoft.com/en-us/visualstudio/profiling/profiling-feature-tour
  [1]: https://i.stack.imgur.com/qbv0D.png
  [2]: https://i.stack.imgur.com/jmFgE.png
  [3]: https://i.stack.imgur.com/cirQu.png
  [4f]: https://i.stack.imgur.com/qLQpL.png
  [4l]: https://i.stack.imgur.com/qLQpLl.png
  [5]: https://i.stack.imgur.com/ppghx.png