Check the timing code for MiniProfiler integration

[Turnerj]

I have a feeling I might have done something wrong in the way the MiniProfiler integrates with the querying code. The problem looks like it would be because I only notify MiniProfiler on the first read and at the end of the whole read, not for every individual item.

Is the point because the query is actually performed to get the first result and the rest of the time the DB is actually waiting on us? Should I be also stopping the timing then on the first read?

I need to sanity check my implementation against the EF Core diagnostic listener again: https://github.com/MiniProfiler/dotnet/blob/master/src/MiniProfiler.EntityFrameworkCore/RelationalDiagnosticListener.cs

[Turnerj]

In b14910f there is a new test that specifically triggers the case that raised this issue. Basically the time during enumeration, that is counted in the diagnostic timing. The first read is the only "valid" one.

At the end of enumeration (specifically at the disposal of the enumerator) is when the timing ends.

I wonder if the idea is to actually use ToArray and ToList or just no heavy processing inside the loop. At this point, I'm going to close this off as I'm both not sure what I can actually do.