Dapper does not find correct constructor for objects with MySqlDateTime in mySql

When attempting to materialize objects with System.DateTime or MySql.Data.Types.MySqlDateTime, Dapper Query<T>() methods throw this exception:

A parameterless default constructor or one matching signature (MySql.Data.Types.MySqlDateTime Item1) is required for System.Tuple`1[[System.DateTime, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] materialization

Examples:

var date = con.Query<DateTime>( "SELECT NOW()" ); // works
var date2 = con.Query<Tuple<DateTime>>( "SELECT NOW() as Item1" ); // throws above exception
var date3 = con.Query<MySql.Data.Types.MySqlDateTime>( "SELECT NOW()" ); //works
var date4 = con.Query<Tuple<MySql.Data.Types.MySqlDateTime>>( "SELECT NOW() as Item1" ); // throws similar exception as above
var my = con.Query<Tuple<long, string>>( "SELECT 1 as Item1, 'tab' as Item2;" ); // works, tuples are correctly populated from Dapper for non-datetimes
var date5 = con.Query<Tuple<DateTime>>( "SELECT GETDATE() as Item1;" ); //tsql, this does work

This bug also occurs with other wrapper types:

class Wrapper
{
    public Wrapper(MySql.Data.Types.MySqlDateTime x)
    {

    }
}
var wrap = con.Query<Wrapper>( "SELECT NOW() as x" ); // throws "Additional information: A parameterless default constructor or one matching signature (MySql.Data.Types.MySqlDateTime x) is required for Wrapper materialization"

This occurs with MySql 4.1 / MySql.Data 6.2.5

Start by reproducing the failure through the Query() examples for Tuple, Tuple, and Wrapper. Trace Dapper's constructor selection and materialization for provider-returned MySqlDateTime values; done means these wrapper and tuple queries materialize successfully while existing non-datetime tuple queries continue to work.