QueryAsync<Dynamic> should return an IEnumerable<DapperRow>

Updated dead link

Replaced dead link (http://rob.conery.io/helpy-stuff/and-i-shall-call-it-massive) to go to Github repository (https://github.com/robconery/massive).

In `QueryAsync<Dynamic>` you will get back an `IEnumerable<object>` requiring you to use `.Cast<IDictionary<String,Object>>()` to get the desired behavior.
However, `Query` returns an `IEnumerable<DapperRow>` so you can use a simple cast or as to  `IEnumerable<IDictionary<string,object>>`

I propose this change to allow this code to just work::
```csharp
var rows = await QueryAsync(cnn, sql) as IEnumerable<IDictionary<string,object>>;
```

Case-insensitive matching support for where-in pseudo parameters

Spell Checking

Just correcting some typos.
One thing that is a matter of opinion. I think recordset and  featureset should not be used as a word so I changed it to => record set and feature set.

whack at an explicit constructor attribute

Fix issue 178: ExecuteReader now returns a wrapper around the command/reader pair, so that the lifetime of the command is extended

Also improve documentation around use of "dynamic" in Query()

Actually pass IsInclusive param to Clause so OrWhere can work

Mention PostgreSQL

It seems worth mentioning explicitly if Dapper works with PostgreSQL or not. I assume it does based on the remark that "it works across all .net ado providers", but am not sure because it's not mentioned explicitly...

Allow passing an IDictionary<string, object> as parameter object

Allows use of IDictionary<string, object> as parameter objects.
I'm assuming that the && was a mistake, and that this logic should
handle both of the types equally well.
Also allows .NET 3.5 to use the IDictionary case.

Revert "Escape column names"