title: Dapper can't ignore nested objects for parameter?
body: <p>I am beginning to use Dapper and love it so far. However as i venture further into complexity, i have ran into a big issue with it. The fact that you can pass an entire custom object as a parameter is great. However, when i add another custom object a a property, it no longer works as it tries to map the object as a SQL parameter. Is there any way to have it ignore custom objects that are properties of the main object being passed thru? Example below</p>
  
  <pre><code>public class CarMaker
  {
  public string Name { get; set; }
  public Car Mycar { get; set; }
  }
  </code></pre>
  
  <p>propery Name maps fine but property MyCar fails because it is a custom object. I will have to restructure my entire project if Dapper can't handle this which...well blows haha</p>