ISO 26262 does not to my knowledge require formal verification, and some googling around seems to support this. Without access to the actual specification I cannot find out exactly what it requires.
So you don't know what's in the standard, but you make assertions and continue to support them? That's a fairly disappointing level of discourse for HN. It requires a very similar software development process to all other functional safety standards, in which verification and validation are key steps.
Here is a paper from Mathworks describing verification and validation according to ISO 26262:
I know how ISO standards are implemented in two unrelated fields, that was really the basis for my comment. Besides, I am now certain that it does not require formal verification, as several companies sell products that support formal verification as a mean to pass the verification part of the ISO.
I'm not going to pay for access to the standard just for a comment on HN.
When you say European manufactures are required to follow this, what about non European manufactures?
Here is a paper from Mathworks describing verification and validation according to ISO 26262:
http://www.mathworks.com/tagteam/71300_1D-4.pdf