Jacques, SHA1 and MD5 are the same kind of technology; they are both one-way hashes. Either could be used for password-type fields. Originally, it was MD5. I added an ability to have different hashes(I stored the hash type in the database), then added salt ability(as a prefix).
The examples given are for password-type fields. As that support has been around for quite a while now, this issue can be closed.
Additionally, if you really are concerned about encrypted fields not having a salt, then svn trunk now supports such a feature. In the entitymodel definition, you can set encrypt="salt", and the value saved to the database will have a salt pre-pended. Note, that if you do this, then you will not be able to do direct lookups against that value.