Update open zeppelin and oraclize

[kostind]

Please check if the PR fulfills these requirements

• The commit message follows our Submission guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

Update OpenZeppelin and Oraclize

What is the current behavior?

(You can also link to an open issue here)

What is the new behavior?

(Define and describe any new functionality. Clarify if this is a feature change)

Does this PR introduce a breaking change?

Run "npm install" to update version of openzeppelin-solidity.

Any Other information:

[kostind]

New version of Ownable contract emits OwnershipTransferred event in a constructor.
I had to replace tx.logs[1].args._ticker on tx.logs[2].args._ticker, tx.logs[1].args._securityTokenAddress on tx.logs[2].args._securityTokenAddress, etc

[satyamakgec]

@kostind could you please remove the conflicts so I can approve the PR.

[maxsam4]

Hmm, PR Travis build is broken.

[kostind]

@kostind could you please remove the conflicts so I can approve the PR.

@satyamakgec done

[kostind]

Hmm, PR Travis build is broken.

@maxsam4 npm run wintest -> 935 passing (5m)
Which command does Travis build use?

Confilcts in package.json were resolved recently.
Could it be the case of failure?

[maxsam4]

@kostind The push commit is building fine even in Travis as well. Pull PR merges the files and runs coverage.
npm run wincov will be the nearest command to it.

I resolved the package.json conflicts and it could be that something went wrong there. unlikely though.

[kostind]

@maxsam4 I tried to resolve conflicts as well, but you won.
I ran npm run wincov locally.

[kostind]

I've got the same result locally for npm run wincov

[maxsam4]

I've got the same result locally for npm run wincov

Just confirming, From the same result, You mean it timed out as well?
Interesting. I'll have to take a deeper look.

[kostind]

@maxsam4 Yes, build hangs on the same step.

[kostind]

truffle test test/b_capped_sto.js -> all tests passed

need to fix coverage

[maxsam4]

@satyamakgec Solidity-coverage is now fixed, please review this again.

[adamdossa]

@maxsam4@satyamakgec@kostind Should this be super._burn instead? Or otherwise we should maybe rename our _burn function so we don't clash with the OZ namespace.

[adamdossa]

(bit surprised this actually works as currently written)

[maxsam4]

I was confused by this when I first saw it as well. It works because our _burn() takes an extra parameter. Therefore, it's function overloading and not overriding that's happening here.

[adamdossa]

This is already checked in the _burn call (from _burnFrom)

I put the changes in