Dapper on ODBC - IN statement

I am using Dapper connecting to an ODBC drive via OleDb.

Since this stack overflow post: http://stackoverflow.com/questions/38527197/dapper-where-in-statement-with-odbc it is possible to pass a list as a named parameter which is great :)

However I still have an issue passing a set of parameters that include a list.

Let me give you an example:

This works:

sql = @"select 1 from dual where 1 = ?id1? and 2 = ?id2?"
conn.Query<int>(sql, new { id1 = 1, id2 = 2 });

This works:

sql = @"select 1 from dual where 1 in ?ids?";
conn.Query<int>(sql, new {ids = new[]{1, 2}});

But this throws an AccessViolationException:

sql = @"select 1 from dual where 1 = ?id1? and 2 in ?ids?";
conn.Query<int>(sql, new { id1 = 1, ids = new[] { 1, 2 } });

The description of the exception is: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Is this expected behaviour from Dapper? And if yes, why and how to go around it?

No repository files or tests are named in the issue. Start by reproducing the two-parameter and mixed scalar/list queries through the shown Dapper Query entry point, then inspect how list parameters are expanded for ODBC/OleDb; done means identifying whether the AccessViolationException is caused by Dapper and documenting or validating a supported workaround.