QueryMultiple on sproc with 4 result sets reading too much data on second Read command

I am using Mono v3.12.1 and Dapper v1.40.

I have a stored proc that returns 4 result sets. My code is using a QueryMultiple followed by 4 different foreach loops using unbuffered Read commands. It seems to detect when the first result set ends and moves on to the second one, but then continues to retrieve all of the remaining data from result sets 2-4 via the second foreach loop, and when it gets to the third loop, an ObjectDisposedException is thrown with message: The reader has been disposed; this can happen after all data has been consumed

The code is basically the same as what you have in the documentation at the link below. The only difference is that I'm streaming the data unbuffered using foreach loops (so no .Single or .ToList, although it breaks when I do that as well) and I'm using a SQL Server stored proc instead of inline SQL.
https://github.com/StackExchange/dapper-dot-net#multiple-results

Start with the QueryMultiple entry point and the unbuffered Read calls described in the issue, using the linked multiple-results documentation as the expected usage. Reproduce the stored procedure case with four result sets and compare each foreach loop's consumption; done means every result set is read separately without consuming later sets or disposing the reader before the third loop.