title: AutoMapper - why use Map over DynamicMap?
body: <p><em>Assuming</em> the objects you're mapping with AutoMapper require no custom mappings, is there ever a point in doing this:</p>
  
  <pre><code>Mapper.CreateMap&lt;Src, Dest&gt;(); 
  // ....
  Mapper.Map(SrcObject, DestObj);
  </code></pre>
  
  <p>If no custom mappings are required, does the above approach gain you anything over just using DynamicMap without the need for any prior configuration?</p>
  
  <pre><code>Mapper.DynamicMap(SrcObject, DestObj);
  </code></pre>
  
  <hr>
  
  <p>I do understand that <code>DynamicMap</code> is <em>required</em> when you're mapping anonymous types, but I'm asking about whether <code>DyanmicMap</code> is ever <em>not preferred</em> for static types that require no custom mappings.  </p>