Stolen bytes were introduced abt 1.5 years ago... no official version because Aspr version are never known, its website is stuck with 1.20 i think... some softwares uses stolen bytes, some dont depending on aspr setting... i fail to appreciate why this is so relevant ?

int3 on Aspr will work but be careful because Aspr has self-crc check which will throw up an error and exit if it detects int3 breakpoints.

TO be honest, anti-unpacking tricks are numerous in aspr, from anti manual tracing to obfuscation... again i dont think it is relevant until you encounter difficulty... it is too general to just talk about everything now... just go on with what u have n you will learn slowly... try not to suffocate in too much new information

Now you can move on to fixing IAT and achieving a 'fair' dump or you can try downloading other aspr protected programs and work on OEP... find one with stolen bytes and you will see how it make finding OEP hard