Additional protection from possible stackoverflow

We are going to use Jint in the production at the back-end of highly customizable cloud web application. The source of the scripts will be our users so we can not trust to the scripts. Moreover if user accidentally writes script which causes stackoverflow it will shut down the whole application. As soon as we can not afford it we will use in production version of Jint with two additional options preventing uncontrolled recursion as a main source of accidental stack overflows. 
See unit tests to get an idea how is going to be used.
Nice catch. At first I was comparing only CallExpression. Then I have found use case tested in the ShouldDiscardHiddenRecursion and that is where .Function comparison was added. Fixed.