Dapper - reader.IsConsumed is false even after reading the last resultset

I am using Dapper version 1.42.0 and SQL Server as the back end to read multiple result-set by executing a Stored Procedure. The issue is that the IsConsumed property of the reader object is false when the last result-set uses spiltOn option to create multiple objects.

This isn't an issue most of the time as this occurs on the result-set, but in my case I have three result sets in which the last set is optional and the 2nd set uses splitOn option to create multiple objects. I use the reader.IsConsumed to determine whether to Read the last result-set or not and in cases when the stored procedure returns only 2 sets I receive an ObjectDisposed error when the code proceeds to read the 3rd set

Reproduce the behavior with Dapper 1.42.0, SQL Server, and a stored procedure returning three result sets, with splitOn used in the second set and the third set optional. Start from the multi-result reader and IsConsumed behavior; done means the final result set is recognized correctly and an absent optional set does not cause ObjectDisposed when read.