What steps of a matrix multiplication could Unity possibly be skipping to make an optimization? The optimization is possible because a scaling and rotation needs only a 3x3 matrix and another vector for the translation, so part of the full 4x4 matrix is unused and can be ignored.
Here is the source code taken from the decompilation [here][1]:
public Vector3 MultiplyPoint(Vector3 v)
{