The current InputFilter component already retains the raw values, and the new InputFilter proposed by Bakura (which seems will be used for 3.0) retains the raw and filtered values.
We can still access to the raw values using InputFilter even if the validator result does not contain it.
When using validators without InputFilter, the raw value is passed to the validator, so the raw value is already available.
If ValidationErrorMessage instances must use the raw value, it could be passed by the validator to the ValidationErrorMessage constructor in the same way that contextual variables are.
As validators are now stateless, the raw value used to validate is a contextual variable.
@matthew, @ocramius Anyway, I understand your points of view, but we can consider not keeping the value in the result of validator.