Consider omitting the contract storage state copy during dBFT system contract calls #154
Description
Rationale
#147 introduces the updated scheme of validators calculations based on Governance contract. In this scheme contract storage state is being copied before the call to Governance contract. Technically, the contract itself doesn't change the state in getCurrentValidators processor (at least, at the current version), and we don't need to create a copy of state. But I'm not sure whether processing engine makes changes in the state. And if not, then state may be used directly without copying.
Ref. #147 (comment).