Remove send/transfer warnings in README & docs

Author: cgewecke

README.md

@@ -110,7 +110,6 @@ Solutions to common problems people run into:
 + [Running truffle as a local dependency](https://github.com/sc-forks/solidity-coverage/blob/master/docs/faq.md#running-truffle-as-a-local-dependency)
 + [Integrating into CI](https://github.com/sc-forks/solidity-coverage/blob/master/docs/faq.md#continuous-integration-installing-metacoin-on-travisci-with-coveralls)
 + [Why are asserts and requires highlighted as branch points?](https://github.com/sc-forks/solidity-coverage/blob/master/docs/faq.md#why-has-my-branch-coverage-decreased-why-is-assert-being-shown-as-a-branch-point)
-+ [Why are `send` and `transfer` throwing in my tests?](https://github.com/sc-forks/solidity-coverage/blob/master/docs/faq.md#why-are-send-and-transfer-throwing)
 
 
 ### Example reports

docs/faq.md

@@ -115,13 +115,6 @@ Clearly, the coverage should be the same in these situations, as the code is (fu
 
 If an `assert` or `require` is marked with an `I` in the coverage report, then during your tests the conditional is never true. If it is marked with an `E`, then it is never false.
 
-### Why are send and transfer throwing?
-
-If you include contracts that have fallback function in the list of files to instrument and attempt to `send` or `transfer` to them,
-the methods will throw because the instrumentation consumes more gas than these methods allow. See the `skipFiles` option in the
-README to exclude these files and [issue 118](https://github.com/sc-forks/solidity-coverage/issues/118) for a more detailed discussion. This problem persists in v0.6.x even though the vm is set to emit free logs.
-(Under investigation).
-
 ### Running on windows
 
 Since `v0.2.6` it's possible to produce a report on Windows (thanks to [@phiferd](https://github.com/phiferd),