Performance improvement of ActionBlock on the posting side

Issue: https://github.com/dotnet/corefx/issues/243

One of the main scenario where ActionBlock is expected to be used is direct posting to it via Post method. The instance method was added only for performance reasons.
 But there is still opportunity to improve its perf by up to 60%.
 Changes are fairly small and simple.
 
Here is microbenchmarking results for the current and updated ActionBlock for x64 build on ultrabook level Intel i7 processor:

============= Current ActionBlock results ==================
 ActionBlock[int]. Million times a sec:
 48,882
 48,781
 47,528
 46,906
 30,912

ActionBlock[object]. Million times a sec:
 39,113
 38,321
 37,792
 37,439
 19,728

ActionBlock[WideStruct]. Million times a sec:
 12,944
 10,377
 10,066
 8,754
 8,46

============= Updated ActionBlock results ==================

ActionBlock[int]. Million times a sec:
 80,048
 74,754
 70,859
 67,143
 30,164

ActionBlock[object]. Million times a sec:
 57,761
 56,573
 54,980
 33,335
 32,809

ActionBlock[WideStruct]. Million times a sec:
 18,357
 16,191
 10,233
 9,483
 8,209

Have you measured the impact of this change on the non-SingleProducerConstrained case?  While I agree the overall change is a good win for the SingleProducerConstrained=true case, it appears to have a negative impact on the SingleProducerConstrained=false path by making it longer.  It may still be worth taking the change, but it doesn't appear to be cut-and-dry.