Add 'Miscellaneous' section & Coveralls badge

Author: Arnd R. Strube

_includes/header.html

@@ -22,6 +22,8 @@ <h2>CppUTest unit testing and mocking framework for C/C++</h2>
 	        <div class="navbar navbar-inverse">
 		        <div class="navbar-inner">
 			        <a class="brand" href="index.html">CppUTest</a>
+			        <a class="brand" href='https://coveralls.io/github/arstrube/cpputest?branch=master'><img src='https://coveralls.io/repos/github/arstrube/cpputest/badge.svg?branch=master' alt='Coverage Status' /></a>
+
 			        <ul class="nav">
 			        	<li class="divider-vertical"></li>
 				        <li><a href="manual.html">Core Manual</a></li>

mocking_manual.markdown

@@ -27,6 +27,7 @@ The main idea is to make manual mocking easier, rather than to make automated mo
 * [MockSupport Scope](#mock_scope)
 * [MockPlugin](#mock_plugin)
 * [C Interface](#c_interface)
+* [Miscellaneous](#miscellaneous)
 
 <a id="simple_scenario"> </a>
 
@@ -495,3 +496,21 @@ mock_c()->clear();
 {% endhighlight %}
 
 The C interface uses a similar builder structure as the C++ interface. It is far less common in C, but it works the same.
+
+<a id="miscellaneous"></a>
+
+### Miscellaneous
+
+If you expect several identical calls, for example five calls to productionCode, you can also use:
+
+{% highlight c++ %}
+mock().expectNCalls(5, "productionCode");
+{% endhighlight %}
+
+If you want your test to be more explicit about that a certain mocked function call should not occur, you can write (v3.8):
+
+{% highlight c++ %}
+mock().expectNoCall("productionCode");
+{% endhighlight %}
+
+Doing so is functionally equivalent to stating no expectations at all.