It makes sense for the reasons how DeepScreen works.
DeepScreen will get triggered on any executable that isn't recognized as safe by the cloud lookup. Meaning, if you're a programmer, every time you code a new EXE file, you essentially create a brand new, unique, never seen by anyone before file. Which WILL trigger DeepScreen for obvious reasons because new malware has the same characteristics (a brand new file not seen by anyone before). There is no way bypassing this other than excluding a compile folder during production and wait for file to get whitelisted by the avast! cloud once you actually publish it. Or if you have it signed by a verified digital signature, you can get in touch with avast! team to discuss whitelisting. I know it's possible but I don't know what are their terms and if they do it only for big companies or also for smaller productions.
I've experienced the same when I was releasing portable Adobe Flash Player as SFX EXE. avast! DeepScreen was triggered every time because those packages were always unique and never before seen by anyone.