fix issue

Author: shargon

src/Neo.SmartContract.Testing/README.md

@@ -473,4 +473,3 @@ The currently known limitations are:
 
 - Receive events during the deploy, because the object is returned after performing the deploy, it is not possible to intercept notifications for the deploy unless the contract is previously created with `FromHash` knowing the hash of the contract to be created.
 - It is possible that if the contract is updated, the coverage calculation may be incorrect. The update method of a contract can be tested, but if the same script and abi as the original are not used, it can result in a coverage calculation error. 
-- Some native contracts use the values of `CallingScriptHash` and `EntryScriptHash` for certain actions, such as `CheckWitness`, so overriding the syscalls with `OnGetEntryScriptHash` and `OnGetCallingScriptHash` could fail.

src/Neo.SmartContract.Testing/TestingApplicationEngine.cs

@@ -32,8 +32,7 @@ public override UInt160 CallingScriptHash
         {
             get
             {
-                var currentHash = InstructionContext.GetScriptHash();
-                var hash = Engine.OnGetCallingScriptHash?.Invoke(currentHash);
+                var hash = Engine.OnGetCallingScriptHash?.Invoke(CurrentScriptHash);
 
                 if (hash is not null)
                 {
@@ -51,8 +50,7 @@ public override UInt160 EntryScriptHash
         {
             get
             {
-                var currentHash = InstructionContext.GetScriptHash();
-                var hash = Engine.OnGetEntryScriptHash?.Invoke(currentHash);
+                var hash = Engine.OnGetEntryScriptHash?.Invoke(CurrentScriptHash);
 
                 if (hash is not null)
                 {