Allows a class to have a reserved word as a column name.

Insert failed when a word such as order was used as a column name.
Added [] around the column name.

Also modified the test for InsertGetUpdate().  The first Get is now a
User instead of IUser.  There is some bug where using the interface
twice first on a null result and then on the real result causes the
reader to not be open when trying to map the type.

Dapper row

Replaced FastExpando with DapperRow/DapperTable. The primary motivation for this is increased performance when creating lot of rows. In addition DapperRow has a smaller memory footprint.

Pull request 55 (thanks: haeal), with some tweaks; better handling of shutting down the data-reader on the happy path

Applied partial to all Dapper classes and interfaces in order to improve extensibility

Multi-Mapping issue with SplitOn

Dapper by source to extend the Dapper classes without making changes to
the Dapper source (for instance in order to expand DynamicParameter with
a method HasValue<T>(string name)). In addition to further help developers
that reference Dapper by source the public property of Dapper classes are
moved to separate partial classes. By default the previous behavior is kept
but when referencing by source you can now make the Dapper classes internal
by defining: DAPPER_MAKE_PRIVATE

There was a small issue when SplinOn spaces between commas, for example:
splitOn: "AddressId, Id".
For more info see:
http://stackoverflow.com/questions/11042618/dapper-multi-mapping-issue

I have modified below line of code:
From: var currentSplit = splits[splitIndex];
To: var currentSplit = splits[splitIndex].Trim();

Also added a test called:
TestMultiMappingWithSplitOnSpaceBetweenCommas()

Ensure that when processing bools we do a "!=0" test; we don't just want to store `7` as a bool - that causes problems sometimes.

Minor deploy glitch (should now include intellisense files!)

Signed-off-by: Marc Gravell <marc.gravell@gmail.com>

Fixed issue with incorrect generated ParamReader when it has indexing properties declared.

IL level type-remapping, so i8 / i4 are interchangeable, etc. This avoids issues on databases that return 1 as bigint by default, etc

Support of types for Id column in Dapper.Rainbow

From time to time ID column has types different to int. With this change
you could specify column type if it is different to int. Example:
public Table<MyDb, Guid> Users { get; set; }

Minor tweaks to custom type-map implementation; principally, lock-less reading and caching the default type-map

Conflicts:
	Dapper.Rainbow/Database.cs