Function Inspection displaying wrong number of semantically identified API calls per function

[Daniel Plohmann]

This bug was introduced by earlier refactoring of idascope.core.SemanticIdentifier.scanByReference() and idascope.core.SemanticIdentifier._createFunctionContext(). _createFunctionContext() is not able of identifying the proper function entry because of an argument mismatch. Fix: normalize the parameter (an address) given to _createFunctionContext() reflect the function address this address is located in.

[Daniel Plohmann]

Fixed Issue #11

→ <<cset 3b1b8a6b99db>>